home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr28
/
bpt5107.zip
/
BUGS.511
< prev
next >
Wrap
Text File
|
1993-03-01
|
11KB
|
236 lines
Below is a listing of the patched products. In parenthesis () is the
environment for which the patch was created.
The information contained in the square brackets [] is a cross reference
to the patch information contained in the BUGS.510 file.
(EG. XREF v5.10 PATCH #14 translates as PATCH #14 in the BUGS.510 file)
Bug descriptions for : BTRIEVE v5.10 PRODUCTS FOR NETWARE 3.1
BTRIEVE,
BROUTER (NLM),
BREQUEST (NLM)
1. Btrieve (NLM) [XREF v5.10 PATCH #14]
An incompatibility with the rest of the Btrieve products:
The Get Position operation following a Delete operation returns
status 43 instead of status 8.
2. Btrieve (NLM) [XREF v5.10 PATCH #19]
Without this patch various random error status can be returned when using
variable length pages or using truncation.
3. Btrieve (NLM) [XREF v5.10 PATCH #21]
The Btrieve function to compare INTEGER keys will sometimes not
recognize a negative value, such as 8000h, as the lower value, treating
it as unsigned instead.
( This patch was originally buggy and had to be corrected on 29Oct90. )
4. Btrieve (NLM) [XREF v5.10 PATCH #22]
If 1. User1 and User2 have different files open ( A and B ) and
2. User3 also opens file A and
3. User4 also opens file B while
4. User2 is simultaneously CLOSING file B
a timing window may appear which causes a divide-by-0 GPI. This patch
corrects a semaphore to fix this.
( This patch was modified on 29Oct90 to allow correction to #21, above. )
5. Btrieve (NLM) [XREF v5.10 PATCH #24]
Get Key-only operations are erroneously not updating the position block.
6. Btrieve (NLM) [XREF v5.10 PATCH #26]
If a Btrieve file has a ZSTRING or LSTRING key using alternate collating
sequence then a key value of length 0 for that key can result in some
undeterministic error due to an uninitialized variable.
7. Btrieve (NLM) & BREQUEST [XREF v5.10 PATCH #27]
For data-only files, Btrieve was returning data to the key buffer
after Get Direct, Update, Insert and Extended Insert.
*** THE PATCH MUST BE MADE BOTH TO THE VAP (OR NLM) AND THE REQUESTER ***
THE VAP (OR NLM) SENDS A FLAG TO THE REQUESTER- IF YOU DON'T PATCH
THE REQUESTER THE FLAG WILL NOT BE UNDERSTOOD AND THE PROBLEM WILL
STILL BE PRESENT.
8. Btrieve (NLM) [XREF v5.10 PATCH #29]
This fixes a bug where a file opened by Btrieve on the server could
not be opened for read-only by a non-Btrieve application, even though
the file had the Shareable attribute set by the Netware FLAG utility.
9. Btrieve (NLM) [XREF v5.10 PATCH #32]
This fixes a bug in an undocumented Btrieve function call, used by
Netware SQL. Only apply this patch after applying patch #27!
10. Btrieve (NLM) [XREF v5.10 PATCH #33]
This fixes the following bug: after a Get Direct returns a status 22
(user's data buffer too small), the user's key buffer was being
overwritten with garbage. It also fixes a bug in which the NLM
was not returning a key value after a Get Direct returns a status 22
when the user's data buffer WAS long enough to at least receive the
fixed length portion (including the keys) of the record.
*** THIS PATCH WILL ONLY WORK IF PATCH #27 HAS BEEN APPLIED TO THE ***
NLM AND BREQUEST.EXE !!!
11. Btrieve (NLM) [XREF v5.10 PATCH #37]
Fixes a bug which caused Btrieve to return an incorrect status 2
when deleting a record from a file with a supplemental index.
This bug is most likely to occur only if few records have been inserted
since the creation of the supplemental index. The bug only occurs
on the VAP or DOS if the supplemental index was created with the NLM.
12. Btrieve (NLM) [XREF v5.10 PATCH #47]
When many workstations are constantly updating the same file, a timing
window can appear which results in cache corruption. The effects can
range from file corruption to abends due to divide/by/zero or processor
exception interrupts.
13. Btrieve (NLM) [XREF v5.10 PATCH #48]
When ending a transaction on multiple files of different page sizes, the
cache can become corrupted, causing the next reader of a file in the
cache to get errors #15 and/or #52.
14. BROUTER (NLM) [XREF v5.10 PATCH #49]
This patch forces only one connection per server and serializes
client threads to avoid an as-yet-unexplained SPX hang.
15. BROUTER (NLM) [XREF v5.10 PATCH #50]
This patch fixes the SPX hang mentioned above and may be used instead
of patch #14. (using both patches is equivalent to using just #14) This
allows up to 3 BRouter-Btrieve connections to a given server and may
result in improved performance in some cases.
16. Btrieve (NLM) [XREF v5.10 PATCH #57]
This bug caused a GET_NEXT to fail with a status 8 immediately after
an extended insert, but only if the insert followed an open call.
17. Btrieve (NLM) [XREF v5.10 PATCH #59]
Multiple segmented null keys are not working; they either inserted into
the index (if duplicates are allowed) or the first occurrence is inserted
into the index and status 5 is returned for the rest of the time (if
duplicates are not allowed).
18. Btrieve (NLM) [XREF v5.10 PATCH #60]
For a KEY-ONLY file which is small enough to fit on a single page, the
operations sequence OPEN-GET LAST(KEY)- GET PREVIOUS(KEY) [0-63-57] can
cause the server to hang in a loop.
19. Btrieve (NLM) [XREF v5.10 PATCH #61]
An Extended Insert called with a data buffer of all 0's (no data) would
return a random, uninitialized error value instead of the correct #63.
20. Btrieve (NLM) [XREF v5.10 PATCH #63]
Btrieve may return a status 9 (End of File) prematurely when Step Direct
is used to retrieve records from a file with greater than 65,535 pages
(i.e., at least 32 megabytes, depending on page size).
21. Btrieve (NLM) [XREF v5.10 PATCH #66]
This fixes a bug in an undocumented Btrieve function call, used by
XQL and NetWare SQL. The bug caused Netware SQL/XQL to return a
status 25 when logging in.
22. BROUTER (NLM) [XREF v5.10 PATCH #68]
This fixes an interface problem between both BROUTERs and the Btrieve NLM
when doing an update operation on a key number other than 0. In some
cases this could result in over-writing the front of the record.
23. Brequest.exe [XREF v5.10 PATCH #70]
Brequest would not completely fill its data buffer, returning #97 for
a 4096-byte record, even with a /D=4096 parameter. (but only if the
key was also maximum length)
24. Btrieve (NLM) [XREF v5.10 PATCH #71]
When an application does a Step Next or Step Previous (or Extended
Step Next/Previous) after a Delete, Btrieve should return a status
8, Invalid Positioning. Instead, this bug causes it to go into an
endless loop. With the VAP & NLM, the workstation will appear to be
hung, too. This patch fixes that bug. (The bug only appears if the
record deleted has a physical position > 0xffff.) Also fixed is a
related symptom of this bug: DOS, Windows and OS/2 Btrieve incorrectly
return a status 0 if you do a Get Position after a Delete.
25. Btrieve (NLM) [XREF v5.10 PATCH #72]
If station #1 is doing GETEQUALs with a key and client #2 is doing
DELETES on the same file using a different key, the system can sometimes
get confused about which key was last used by #1, returning a status 7.
26. Btrieve (NLM) [XREF v5.10 PATCH #75]
XQLP and SQL returned status 82 on a user-defined sort at the NLM due
to a bug in an undocumented Btrieve function.
27. Btrieve (NLM) [XREF v5.10 PATCH #80]
In certain cases when an UPDATE fails for Duplicate Key (Error 5) the
update operation may not be undone properly. This can result in
subsequent status 9s or 4s on a GET_EQUAL for a limited number of other
keys which may have been corrupted by this failure. This bug corrects
the preimaging call to fix this.
28. Btrieve ( NLM ) [XREF v5.10 PATCH #86]
After an Update is done on a file with compressed records, positioning
is lost. A Get Position will return a status 8; a Get Next will skip
to the next key value, ignoring the next duplicate, if any. Similarly,
after an Insert is done on a file with compressed record, a
Get Previous will skip to the previous key value, instead of the
previous duplicate, if any.
29. BTRIEVE ( NLM ) [XREF v5.10 PATCH #87]
Sometimes a DELETE following a STEP_FIRST, then STEP_PREVIOUS
would return a conflict status 80 because the position was lost on the
failed STEP_PREVIOUS (error #9). This fix restores the position.
30. BTRIEVE (NLM) [XREF v5.10 PATCH #88]
A Conflict error (status 80) is returned when Updating or Deleting,
even though there is only one workstation accessing the file. This
bug will only appear if the record being updated/deleted contains
a certain pattern of data: all bytes except the first four must be
binary zeroes, and some other, complicated conditions must be met.
31. BTRIEVE (NLM) [XREF v5.10 PATCH #89]
When two clients are pointing at the same record in a file and one of
them does an update which changes its key, the second client will get
an unpredictable, out of sequence record on his next GetNext. This
patch makes his current record invalid but leaves the next and previous
pointers alone to maintain the relative position for that second user.
32. BTRIEVE (NLM) [XREF v5.10 PATCH #94]
Fixes a problem in patch 31 which causes the following problem: after
an Update which changes a record's key value, a subsequent
Get Previous skips any records whose key value is a duplicate of
the (new) key value of the record which was just changed.
***** Last Update - 05/30/91 - MJH *****